home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
sbbshslk.zip
/
DSZ2ICOM.ZIP
/
DSZ2ICOM.DOC
next >
Wrap
Text File
|
1992-02-18
|
10KB
|
182 lines
==============================================================================
DSZ2ICOM
Martin Schnitkemper
Postbox 7462
W-4400 Münster
==============================================================================
Introduction:
------------
This application is designed to run under QuickBBS or a compatible system like
RemoteAccess or even SuperBBS in conjunction with a filetransfer manager like
EFT. It is running under MS-DOS v5.00_D, SuperBBS v1.16 beta-1, EFT v1.21ßb
and the HS/Link protocol v1.01.
The Problem:
-----------
Usualy the most filetransfer manager can only handle either an up- or a
download and get confused with any bidirectional protocol like BiModem. Erik
Labs created a new logformat, named the "Intercommunication Logfile" and it
seems to be that this format becomes standard for bidirectional protocols. If
you are one of the lucky guys who used EFT (not only for this reason), this
filetransfer manager support the usage of the intercom logfile. Unfortunately,
at this moment only BiModem creates this intercom logfile and can only used as
an realy bidirectional transfer protocol.
The recently released new transferprotocol HS/Link is a bidirectional protocol
but does only create a DSZ logfile. If you install this protocol, you either
lost the account of the up- or the download, depending of the direction.
But don't worry, here comes...
The Solution:
------------
After the filetransfer, DSZ2ICOM reads the logfile, created by HS/Link and
writes a new file out named "INTERCOM.LOG". This file is full compatible to
the BiModem standard. For the structure of this file, please refer the BiModem
documentations. All fields of the DSZ logfile will be converted into the ICOM
style. Unsupported fields will be remainded empty, the time- and datefields
contains the current values.
The Installation:
----------------
The installation is quite easy, if you use already the EFT filetransfer
manager. Please add additional lines like the example
shown below:
;
Protocol 98 H U 64 HS/Link
INTERCOMM DSZ2ICOM HSLINK -P$1 -B19200 -E$2 -HX -S4096 -K -R -O
behaviour getinfos arctest resume
Protocol 98 H D 64 HS/Link
INTERCOMM DSZ2ICOM HSLINK -P$1 -B19200 -E$2 -HX -S4096 $3 -K -UF:\UPLOADS
behaviour arctest leaveuploads
;
Use the INTERCOMM protocol statement instead of DSZ. To get full control over
the HS/Link protocol depending on the transfer direction, use the commandline
parameters. Most of them are optional, read the HS/Link manual for a full
description. I got the best results after erasing HSLINK.CFG.
Don't ask me for other examples as I would'nt never change to another
filetransfer manager than EFT ...
You should know:
---------------
Specify the upload path on the commandline only on downloads. Don't specify
this path with HSCONFIG (you better omit the whole configuration file), let
EFT determine the path on uploads!
An upload, coming together with users download will be placed in this path.
Don't include this path in your FLSEARCH files, use a common one (i.e. the
same as you use with BiModem). In this mode an aborted upload can't recover by
the user, the remaining part will be moved by EFT to your crash directory.
(Enable with the -K switch).
The upload mode gives the user the opportunity to finish a broken upload. EFT
will move the upload to the current area after completion. (Enable with the -K
-R and -O switches).
Set the DSZLOG environment variable. Without it HS/Link does not create a
logfile. I recommend to set it to "DSZ.LOG", without a path specification.
DSZ2ICOM create INTERCOMM.LOG as the logfile. EFT does accept it as the
default, do not set it to another name.
DSZ2ICOM IS FREEWARE: I hereby declare the whole material as public domain,
nor charge or fee maybe given to me or anyone else for this application. Use
it on your own risk so long as you want. Give it away to everyone who need it.
DSZ2ICOM is a subset of SBiLink, the bidirectional protocol driver for
SuperBBS systems.
Revision History:
----------------
18.02.92 v0.09 ■ Since HS/Link v1.01 returns related log entries after
aborted transfers, I removed the detection from coding.
NOTE: This version of DSZ2ICOM does no longer work with
releases of HS/Link previous to v1.01, so you have to
upgrade now!
■ The history file is no longer written. Non (are there
still any?) EFT users: DSZ.LOG will remain for debugging
reasons until the next session of DSZ2ICOM starts.
■ Filename in INTERCOM.LOG had trailing spaces. Terminating
now with a binary zero (ASCIZ).
■ HS/Link can't pass a file description, set the
corresponding field in the INTERCOM.LOG today to 80
spaces.
■ HS/Link v1.01 returns now a cps of 9999 if a received file
already exist in the same subdirectory and the
verification did not failed. In this case DSZ2ICOM set the
status to "D" to indicate a duplicate upload. It seems
that you can specify now the -K, -O, -R and -U switches in
both ways without problems.
17.01.92 v0.08 ■ Runtime error occured while searching for existing files.
Changed the procedure, hope to fix this bug.
09.01.92 v0.07 ■ Improved again the handling of aborted transfers, it
should now work correctly if you follow the instructions
and examples, mentioned above. DSZ2ICOM determines now the
transfer direction in to steps: On uploads it scans the
current directory for the aborted file. If it is there, it
must be an aborted received file, if not it was an attempt
to send. On downloads it scans in the given upload
directory. For this reason you have to use the -U switch
to tell HS/Link (and even DSZ2ICOM) the upload path.
Define the upload path no longer with HSCONFIG.
■ The direction of an aborted transfer will be indicated by
a single letter in brackets as a local message on the
screen.
■ If another DSZ.LOG or INTERCOM.LOG is present on your
system and a previously issued append command points to
these paths, unfortunately these files will be updated.
For this reason, both files will be truncated to a null-
length-entry before and after DSZ2ICOM is/was invoked.
Anyway, you are on the safe side if you hold no duplicates
of these files on your system.
05.01.92 v0.06 ■ I got it! To detect the direction of an aborted transfer,
DSZ2ICOM extract now the upload path from the commandline
and compare it with the filespecification, given via the
DSZ.LOG file. If it is equal, the entry will be treated as
a received file, otherwise as a sent one. Note: For proper
operation you *must* now use the -U switch on the
commandline, either if you defined the upload path with
HS-CONFIG or not. Dear Mr. Smith: Create a DSZ.LOG
according to the given standard, thanx!
■ I changed the FileID of the history file today to
"DSZ2ICOM.LOG" due to a buggy GSZ proto driver who updated
the first (and probably wrong) DSZ.LOG file.
■ Reading now the DSZLOG environment variable to
locate/create the DSZ logfile. If the variable is missing,
DSZ2ICOM assume the DSZ.LOG in the current directory and a
warning will be issued.
04.01.92 v0.05 ■ Got still problems with aborted transfers: HS/Link is not
able to differ between sent or received files after a
carrier loss or an abort. Regardless the direction,
HS/Link indicates all aborted transfers in DSZ.LOG with
capital letters. Following the usual logic, these entries
must be treated as received files. Due to the problem of
handling, an entry in the intercomm logfile will no longer
be created in case of aborted transfers. Hope to solve
this problem now. Remeber: You can still resume aborted
uploads, using the -O (overwrite) and -R (resume)
switches.
■ Fixed a bug in the cps calculation: A reported cps over
3200 bps (unusual, but possible after resumption of an
aborted transfer) will be set to a zero value.
03.01.92 v0.04 ■ Kept the first and last two lines of the screen unchanged
to display EFT's informations
■ Creating a DSZ.LOG history file at the root path for
debugging reasons
■ Fixed a bug, handling aborted transfers
16.12.91 v0.03 ■ First release to selected sysops only